Skip to content

Conversation

benmccann
Copy link
Member

@benmccann benmccann commented Oct 23, 2024

while most these would be redirected, this is likely better for SEO. it also fixes a broken link, which alerted me to another set of redirects I need to double check in a follow up

Copy link

vercel bot commented Oct 23, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
kit-svelte-dev 🔄 Building (Inspect) Visit Preview 💬 Add feedback Oct 24, 2024 3:58pm
learn-svelte-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 24, 2024 3:58pm
omnisite ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 24, 2024 3:58pm
svelte-5-preview 🔄 Building (Inspect) Visit Preview 💬 Add feedback Oct 24, 2024 3:58pm
svelte-dev 🔄 Building (Inspect) Visit Preview 💬 Add feedback Oct 24, 2024 3:58pm

@Conduitry
Copy link
Member

Hm. I have really mixed feelings about rewriting history in blog posts. I don't know what to do about this. https://svelte.dev/blog/svelte-4, for example, contrasts learn.svelte.dev with the old tutorial that's still available for certain browsers. Do we update that too now that that distinction no longer exists?

@benmccann
Copy link
Member Author

benmccann commented Oct 24, 2024

Hm. I have really mixed feelings about rewriting history in blog posts. I don't know what to do about this. https://svelte.dev/blog/svelte-4, for example, contrasts learn.svelte.dev with the old tutorial that's still available for certain browsers.

Yeah. I think blog posts have multiple functions. I think this helps with SEO and helps with folks who stumble upon these blog posts now trying to learn how to do something. It might hurt for folks who are trying to act as historians and for some reason needed to know that the tutorial used to live on a separate domain (though I did leave some of those references alone). I'm prioritizing the needs of current users over historians here

Do we update that too now that that distinction no longer exists?

Yeah, good idea

@benmccann
Copy link
Member Author

I fixed the merge conflicts on this. I tried to be judicious about which links and text to update. Happy to revert a couple more if you think that's best. There are a couple in the last post that would otherwise be broken that I definitely think we should update

@Rich-Harris
Copy link
Member

Isn't this what redirects are for?

@benmccann
Copy link
Member Author

I expect there's a negative SEO impact to passing on page rank if you route it through a redirected subdomain.

Plus, we have a lot of broken and missing redirects right now: #619

@Rich-Harris
Copy link
Member

I wouldn't worry too much about SEO — if you google 'svelte tutorial' then the top result is the correct one. And it's not like these specific links are broken in the first place

@benmccann
Copy link
Member Author

benmccann commented Oct 25, 2024

The links in apps/svelte.dev/content/blog/2023-09-20-runes.md are broken

We don't really have anything preventing us from breaking redirects, but if we write these as paths instead of fully qualified URLs then we get the benefit of the link checking. Plus, we've rewritten probably several hundred URLs at this point and these are like the last dozen remaining

….0.md

Co-authored-by: Rich Harris <rich.harris@vercel.com>
@Rich-Harris Rich-Harris merged commit 1e54877 into main Oct 25, 2024
4 checks passed
@Rich-Harris Rich-Harris deleted the learn-svelte-dev-urls branch October 25, 2024 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants